Management of virtual and physical network inventories

ABSTRACT

A method for managing a network element inventory for a video and data network is provided. The method includes self-discovering a physical network inventory of the video and data network. Additionally, a logical network inventory of the video and data network is self-discovered. Further, a planned network inventory of the video and data network is provided. Once the planned, logical, and physical network inventories are collected, the physical network inventory, logical network inventory, and planned network inventory are loaded into the network element inventory. After loading, synchronization of the physical network inventory, logical network inventory, and planned network inventory in the network element inventory is performed. A view is then provided using the synchronized physical network inventory, logical network inventory, and planned network inventory when a request for the view of the network element inventory is received.

CLAIM OF PRIORITY

This application claims priority from U.S. Provisional PatentApplication No. 60/222,791, filed Aug. 1, 2000, entitled “Management ofVirtual and Physical Network Inventories,” which is hereby incorporatedby reference, as is set forth in full in this document, for allpurposes.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is related to and claims the benefit of co-pendingapplications No. 09/921,285, entitled “PROVISIONING SYSTEM AND METHODFOR AUTO-DISCOVERING CUSTOMER PREMISES EQUIPMENT IN ACTIVATING xDSL”;No. 09/921,924, entitled “PERFORMANCE MODELING IN A VDSL NETWORK”; No.09/921,176, entitled “FAULT MANAGEMENT IN A VDSL NETWORK”; No.09/921,277, entitled “FAULT MANAGEMENT IN A VDSL NETWORK”; No.09/921,283, entitled “PROACTIVE REPAIR PROCESS IN THE xDSL NETWORK (WITHA VDSL FOCUS)”; No. 09/921,275, entitled “PROACTIVE SERVICE REQUESTMANAGEMENT AND MEASUREMENT”, and No. 09/921,274, entitled “LINKING ORDERENTRY PROCESS TO REALTIME NETWORK INVENTORIES AND CAPACITIES”, all filedAug. 1, 2001, the disclosures of which are incorporated herein byreference.

BACKGROUND OF THE INVENTION

The present invention relates to the management of virtual and physicalnetwork inventories and more specifically the management of virtual andphysical network inventories of a xDSL network.

As networks providing digital services to consumers are built out toaccommodate more consumers, the networks become more complicated andharder to manage. Additionally, as companies increase capitalexpenditures to build out these networks, more emphasis is focused onincreasing the sales of services that are provided through a network. Ina typical operation, a network may provide data services to and from anInternet Service Provider (ISP) and a consumer. Thus, a user typicallyaccesses the Internet through the network connection. Additionally,video services may be offered through the network to provide a consumerwith additional choices such as cable T.V. from a satellite or cableprovider. With the increase in services, continual build-out of thenetwork, and the exponentially increasing number of consumers added tothese services, it becomes increasingly difficult to manage the assetsof the network.

Companies include departments such as sales, engineering, and marketingthat need different views of the same network inventory. However, evenif the departments interact with the inventory of the network, theinventory is not a complete and up-to-date version. For example, a salesdepartment takes orders from customers on the assumption that thenetwork is physically able to offer service to the customers. However,the sales department takes the order without considering networkcapacity and/or network quality.

Additionally, the marketing department is used to forecast an amount ofcapacity to add to the network. The marketing department, however, doesnot include in-progress network additions or pending sales in theirmarketing forecast and thus, the inventory data used for forecastingcapacity is incomplete. Therefore, forecasts to add capacity to thenetwork may be flawed and inaccurate.

The engineering department designs and builds out the network afterreceiving the marketing forecast. In building out the network, theengineering department plans and installs physical network elements, andassigns virtual paths through the network elements to enable service tocustomers. For example, installing physical network elements includesinstalling network elements and associated cards/ports in the networkelements that enable new customers to receive service. After beinginstalled, identifiers for the new ports/cards are manually entered intoan inventory data base and manually synched between the existing networkelements in the inventory data base. Additionally, InterofficeFacilities and Fibers (IOF) identifiers are manually inventoried. Thus,identifiers for devices such as DSLAMs, routers, fiber components, andother components of the network are manually entered. Also, managementof the assignments of logical paths in the network is manual and arerepeatedly inputted for each network element in the logical path.

Thus, the management of inventory and the access of inventory are manualprocesses. Additionally, although engineering may manually inventoryphysical and logical network designs, the inventory is not accessed byother departments when making decisions. For example, the salesdepartment approves orders for service without referencing any capacityor planned information. Basically, the sales department approves anyorder without verifying if the network has capacity to provide theservice. Also, the sales department does not distinguish betweendifferent services that may be offered through the network. Thus,network capacity may be filled with less profitable services.Additionally, the marketing department produces capacity forecastswithout the knowledge of in-progress network additions.

Thus, the departments are making decisions that are dependent on actionsfrom each group without information of the other group's actions. Thisleads to inefficient management of network inventory.

BRIEF SUMMARY OF THE INVENTION

In one embodiment, a method for managing a network element inventory fora video and data network is provided. In one embodiment, the methodincludes self-discovering a physical network inventory of the video anddata network. Additionally, a logical network inventory of the video anddata network is self-discovered. Further, a planned network inventory ofthe video and data network is provided. Once the planned, logical, andphysical network inventories are collected, the physical networkinventory, logical network inventory, and planned network inventory areloaded into the network element inventory.

After loading, synchronization of the physical network inventory,logical network inventory, and planned network inventory in the networkelement inventory is performed. A view is provided using thesynchronized physical network inventory, logical network inventory, andplanned network inventory when a request for a view of the networkelement inventory is received.

In one embodiment, the video and data network comprises a type ofdigital subscriber line (xDSL) network, such as a Very high bit rate DSL(VDSL) network.

A further understanding of the nature and advantages of the inventionherein may be realized by reference of the remaining portions in thespecification and the attached drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system including components that may be included ina network element inventory;

FIG. 2 illustrates the network of FIG. 1 in more detail;

FIG. 3 illustrates elements of network element inventory;

FIGS. 4 a-d illustrate a process for managing network element inventory;

FIG. 5 illustrates a method for managing a network element inventory;

FIG. 6 illustrates elements of a capacity calculating engineenvironment;

FIG. 7 illustrates a method of determining capacity for a network; and

FIG. 8 illustrates a method for handling customer inquiries for videoand data service according to one embodiment.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 illustrates a system 100 including a network 102 and a networkelement inventory 106. As shown, network 102, an element managementsystem 104, and network element inventory 106 are included.

Network 102 may be any network capable of delivering telephony, or highspeed data to customers. In one embodiment, network 102 is a xDSLnetwork capable of delivering telephony, video, and/or data to customersat high speeds. It is noted for purposes of understanding the presentinvention, the term xDSL is used as a broad label for identifying anumber of different types of digital subscriber line (DSL) signalformats, such as rate adaptive DSL (RADSL), Asymmetric DSL (ADSL),high-bit-rate DSL (HDSL), and very-high-data-rate DSL (VDSL).Compatibility for two or more of these formats within the samedistribution system may also be provided.

As shown, network 102 includes a shared network 108 and a plurality ofcustomer networks 110. Customer networks 110 may be any networkconnecting the customer to shared network 108. A customer network in theplurality of customer networks 110 may be an individual network for onecustomer or a network for a group of customers. Network 102 includes aplurality of network elements that deliver video and data throughnetwork 102.

Shared network 108 may be any network that is shared among plurality ofcustomer networks 110. Shared network 108 handles the flow of telephony,video, and/or data from a service provider and routes signals toplurality of customer networks 110, which in turn, routes the signals toindividual customers. Additionally, shared network 108 includes a videopipe 112 and data pipe 114. Video pipe 108 delivers video to pluralityof customer networks 110 and data pipe 114 delivers data to plurality ofcustomer networks 110. Shared network 108 also may be configured toprovide telephony service to customers, for example through data pipe114, or telephony service may be provided through a public switch at acentral office, as discussed below.

Element Management System (EMS) 104 may be any application capable ofreceiving/discovering data from shared network 108 and plurality ofcustomer networks 110. In one embodiment, EMS 104 is the only systemthat may configure and/or access data from shared network 108 andplurality of customer networks 110. The data received from the networkmay include, for example, performance data, fault data, and an inventoryof network elements. Additionally, EMS 104 may include customer data,which includes data relating customers to designated physical andlogical paths in shared network 108 and plurality of customer networks110. In one embodiment, multiple EMS 104s may be included and discoverdata from various elements to network 102.

Network element inventory 106 may be any database capable of storingdata relating to network 102. In one embodiment, the network elementinventory 106 may receive data from shared network 108 and plurality ofcustomer networks 110 directly thereby removing the need for EMS 104.Network element inventory 106 includes network discovered physicalinventory, network discovered logical inventory, and planned networkinventory in one embodiment.

In FIG. 2, network 102 is shown in more detail according to oneembodiment. As shown, shared network 108 includes an external serviceprovider section (ESP) 200, a video/data operation center (VDOC) 202, aninteroffice facility (IOF) 204, central office (CO) 206, and midloop208. In one embodiment, ESP 200 includes ISP 210 and satellite 212. ISP210 provides access to the Internet and other data services. Satellite212 provides access to video and other video services. While the dataand video providers are shown as ISP and satellite providers, it will beunderstood by a person skilled in the art that other ways of providingvideo and data services are possible.

VDOC 202 includes video pipe 112 and data pipe 114 of FIG. 1. In oneembodiment, video pipe 112 can be configured to deliver video signals toand from ESP 200 and/or IOF 204 through optic fiber, such as OC-12 c,and data pipe 114 can be configured to deliver data to and from the ESP200 and/or IOF 204 through optic fiber, such as OC-3 c. However, inaccordance with other embodiments of the invention, video pipe 112 anddata pipe 114 can utilize any other suitable broadband connectiondeliver the video and data signals, such as other forms of fiber optics,wireless technologies, or the like. Thus, the present invention is notlimited to the illustrated embodiment.

In one embodiment, video pipe 112 delivers video using a videoasynchronous transfer mode (ATM) based protocol. In one embodiment, datapipe 114 delivers data using an Internet Protocol (IP) based protocol.

Video pipe 112 includes a satellite dish 214, video router 216, encoderswitch 218, and ATM network element (NE) 220. Data pipe 114 includes afirewall 222, IP switch network element 224, and switch router networkelement 226. It should be understood that a person of skill in the artwill appreciate other ways of implementing video and data pipes, such asvideo head-ends currently known in the art.

IOF 204 includes synchronous optical network rings (SONET) 248. SONET248 may be any optical network capable of delivering video and data toand from the VDOC 202 and central office 206.

Central Office (CO) 206 includes an ATM router NE 228 and CO DigitalSubscriber Loop Access Module (DSLAM) 230. In one embodiment, CO DSLAM230 may be a broadband digital terminal (BDT). ATM router NE 224 and CODSLAM BDT 230 are coupled to IOF 230 and midloop 208 through opticfiber, such as OC-3 c and OC-12 c. Additionally, CO 206 includes apublic switch 230 and Main Distribution Frame (MDF) 234. Public switch230 and MDF 234 is where an outside customer network is coupled to theshared network. In one embodiment, public switch 232 and MDF 234 providetelephony service to a customer. Additionally, MDF 234 is coupled tomidloop section 208.

Midloop 208 includes a RT DSLAM 236 and may include a crossbox 238.Crossbox 238 provides a connection from shared network 108 to pluralityof customer networks 110. RT DSLAM 236 may include Universal ServiceAccess Multiplexers (USAM), Multiple Dwelling Units (MDUs) and/orBroadband Network Units (BNUs). Additionally, CO DSLAM 230 is associatedto RT DSLAM 236. RT DSLAM 236 may include an Optical Network Unit (ONU),which acts as a router for RT DSLAM 236.

RT DSLAM 236 is a network element that is used to convert optical videoand data signals sent from CO DSLAM 230 into electrical signals fordeployment to the customer locations over electrical cable connections,such as twisted pair copper cable. The electrical signals may becombined with a telephone signal and are sent to customer's locations.By positioning RT DSLAMs 236 closer to customer locations, the reach ofthe high speed data service is extended. In one embodiment, RT DSLAM 236is a node positioned in a neighborhood (fiber-to-the-node deployment)and is configured to convert the optical video and data signals toelectrical signals for deployment to a plurality of customer locationsvia cross box 238 used to serve that neighborhood.

In another embodiment, RT DSLAM 236 is a terminal node forfiber-to-the-curb deployment and feeds service to a customer locationdirectly without the need for cross box 238.

In yet another embodiment, a RT DSLAM 236 is the network element that issuitable for location in a multiple dwelling unit (MDU), such as anoffice or apartment building. In this particular embodiment, RT DSLAM236 is a variation of a terminal for fiber-to-the-node deployment andfeeds service to the customers in the MDU directly and not through crossbox 238 associated with a distribution area (DA).

If midloop 208 includes cross box 238, cross box 238 relays signals fromRT DSLAM 236 from midloop 208 to the customer.

As shown, a customer network in plurality of customer networks 110,includes a home network and/or Customer Premise Equipment (CPE) 240. CPE240 is coupled to the cross box 238 or RT DSLAM 236 if cross box 238 isnot present and receives the video, data, and/or telephony signals. CPE240 may be coupled to a TV 242, workstation 244, and/or telephone 246.Thus, the customer can receive telephony, video, and/or data signalsfrom the network. In one embodiment, CPE 240 may be replaced by otherequipment capable of receiving signals from shared network 108.

It will be understood that a person of skill in the art will appreciateother ways of implementing network 102. Thus, network 102 is not limitedto the above description.

Network Element Inventory

FIG. 3 illustrates elements of network element inventory 106 accordingto one embodiment. As shown, network element inventory 106 includesnetwork discovered physical inventory 302, network discovered logicalinventory 304, and planned network inventory 306. Planned networkinventory 306 may also include planned logical and planned physicalinventory.

Network discovered physical inventory 302 and network discovered logicalinventory 304 may also be parsed and normalized (Step 308) and loaded(Step 310) into network element inventory 106. However, the parsing andloading step may be unnecessary and network discovered logical inventory304 and physical inventory 302 may be directly loaded into networkelement inventory 106. Parsing and loading network discovered physicalinventory 302 and logical inventory 304 is done to normalize datareceived from different network elements because different networkelements may send and manage data in different formats.

Network discovered physical inventory 302 includes physical inventory ofthe network that is self discovered by intelligent network elements ofthe network. Network discovered physical inventory 302 representsinstalled physical inventory of the physical network. In one embodiment,network discovered physical inventory 302 is created daily in elementmanagement system 104. As discussed above, EMS 104 is a centralrepository where self-discovered inventory information from network 102is discovered and retrieved. The total installed inventory includes used(e.g., allocated to a customer), available (e.g., available for customeruse) or possible (e.g., not available for customer use) networkcomponents.

Additionally, network discovered logical inventory 304 includes logicalor virtual inventory of the network that is self discovered byintelligent network elements. In one embodiment, the logical inventoryincludes installed virtual paths and assignments. In one embodiment,network discovered inventory logical inventory 304 may be created in EMS104. The logical inventory also represents the used and availablelogical inventory in network 102.

Planned network inventory 306 includes installed (with only a partial inuse status) inventory, planned inventory, and pre-assigned plannedinventory information.

Planned network inventory 306 may be automated by including tools foroperation systems, such as engineering, sales, and marketing, to enterplanned network inventory into network element inventory 106. Forexample, once the engineering department develops spreadsheets or otherdocumentation representing planned inventory, pre-assignments areentered into network element inventory 106 through a graphical userinterface (GUI).

Additionally, in one embodiment, planned logical inventory is enteredautomatically into network element inventory 106 through a logical pathautomation process that facilitates management of Virtual ChannelIndicator/Virtual Path Indicator (VCI/VPI) pools within the network. Thepools of VPI/VCI links are created to support the flow of video and datato users over the network. The VPI/VCI links include the virtual orlogical path that data is routed through over the physical network. Inorder to implement an automated VPI/VCI managed pool, a centralizedsystem allowing entry of a virtual path into one manager or system orVPI/VCI administration system, which will propagate the same virtualpath into multiple network elements is provided. Thus, the laborintensive task that involved entering the same information for the samevirtual path into multiple network elements or systems (ATM switches,routers, CO DSLAM 230 and RT DSLAM 236) is avoided.

When construction of new equipment is completed or a user's reportindicating that existing capacity is nearly consumed, an assignmentprocess to decide VPI/VCI allocation is initiated. Once the allocationis completed, actual assignment needs to be configured in, for example,routers, ATM switches, CO DSLAM 230 and RT DSLAM 236.

In the VPI/VCI system, an administrator enters the assignments into aVPI/VCI administration system. The system then takes those assignmentsand propagates the appropriate assignments to the network elements.Additionally, the system records the assignments and documents theassignments into network element inventory 106. Thus, multiple manualentries required for the routers, ATM switches, CO DSLAM 230, and RTDSLAM 236 are avoided. Further, the additional task of recording thoseassignments is avoided. Additionally, administrative errors are reducedbecause duplicate multiple entries of assignments do not need to be madeand recorded. Also, when network elements are changed for capacity orfor maintenance reasons, the entry of VPI/VCI information will have tobe repeated for the new switch. However, the VCI/VPI administrativesystem will be able to repeat the location and assignment without anyextra manual steps. Thus, network rearrangement work will not affect theallocation of VCI/VPI assignments.

In one embodiment, the planned network inventory 306 may include CODSLAM 230 (e.g., broadband digital terminal (BDT) information) and/or RTDSLAM 236 information. CO DSLAM 230 information may include, forexample, an IP address, central office ID [CLLI code], relay rack,planned in-service date, number of cards, number ports per card, andplanned job number associated with CO DSLAM 230 installation.

In one embodiment, RT DSLAM 236 information may include, for example,circuit ID of facility back to the central office, distribution area(DA) served by the RT DSLAM 236, wire center ID [CLLI code], cabinet ID[CLLI code], cabinet location (address), associated crossbox address,planned in service date, planned job number associated with RT DSLAM 236installation and the number and type of cards within the RT DSLAM 236.

Additionally, planned network inventory 306 may include plannedassignment (reservation) information. In one embodiment, thepre-assignment data includes CO DSLAM 230 to RT DSLAM 236 assignmentinformation. The assignment information includes how network 102 isconnected from the CO 206 to crossbox 208. In a specific embodiment, theconfiguration and management of the facility connecting CO DSLAM 230with the RT DSLAM 236.

Network element inventory 106 may include a graphical user interface(GUI) to add, change, or delete planned inventory information.Additionally, in one embodiment, the addition or deletion of plannedassignments (reservations) of cards to specific operation systems.Further, the system may provide a display of existing, consumed, spare,and planned additional capacity associated with a given central office230 and/or RT DSLAM 236 location.

By integrating self-discovered, used and available inventory with theplanned inventory, a single, consistent, and consolidated view isrealized. This view may then be customized for access by other operationsystems and organizations.

FIGS. 4 a-d illustrate a process for managing network element inventory106 and for product deployment for a xDSL sales service. In FIG. 4 a, anumber of different operation systems are dependent on having access tonetwork element inventory 106, such as the marketing 404, engineering406, and sales 402 departments. Although sales 402, marketing 404, andengineering 406 departments are used to discuss the multiple operationssystems, it will be understood that other operation systems may beincluded and access network element inventory 106.

The process includes marketing 404 providing a market forecast ofexpected demand and available capacity that needs to be built to meetdemand to engineering 406. Engineering 406 then plans and builds thenetwork and assigns capacity to the network. Marketing 404 monitors theconstruction and provides sales 402 with forecast of capacity that maybe sold.

FIG. 4 b illustrates the engineering process in more detail. As shown,engineering 406 receives the marketing forecast. Additionally,engineering may receive a view of held orders, which are orders thatwere taken but were not filled, from network element inventory 106.Engineering 406 then makes a decision to build new physical networkelements or modify existing physical network elements to increasecapacity. In one embodiment, engineering 406 may build new networkelements and/or modify network elements in either CO 206 midloop 208. Todocument the changes in CO 206 or midloop 208, manual records arecreated to represent new and/or modified network elements and track theconstruction. Additionally, during the engineering design process,engineering 406 determines virtual associations or assignments betweenthe installed network elements. These assignments define the virtual orlogical path of data flow for customers. Engineering 406 also keepsmanual records of the assignments. The physical and virtual inventoriesare then entered into network element inventory 106 as plannedinventory.

In FIG. 4 c, marketing 404 is constantly monitoring the consumption ofcapacity of the network to enable marketing 404 to provide guidance tosales 402. The review is accomplished by querying network elementinventory 106 for a view of planned and self-discovered logical andphysical inventory information. From the view, marketing 404 develops atactical sales plan for sales 402 and a revised capacity forecast forengineering

In FIG. 4 d, sales 402 receives a request for service. Sales 402 queriesnetwork element inventory 106 for network quality and serviceavailability for that specific customer. Using network element inventory106, sales 402 receives a desired view of information and processes theorder based on self-discovered used and available and planned capacity.Additionally, sales 402 may verify network quality.

Synchronization:

In order to ensure each operation system receives an accurate view ofinventory of the network, network element inventory 106 synchronizesnetwork discovered physical 302 and logical inventory with the plannedinventory 306. By synchronizing the network inventory creates anaccurate view of planned inventory 306, self-discovered physical 302,and logical 304 inventory. Typically, different views may be created foreach operation system. For example, engineering 406 may need differentinventory information than sales 402 and/or marketing 404. Thus,different views may be created for each group.

The view of inventory may be created using self-discovered physical 302and logical 304 inventory, planned inventory 306, and comparedself-discovered and planned inventory. In some cases, planned andself-discovered inventory overlap and are compared by network elementinventory 106 to determine if what was thought was built is what wasactually built. If the comparison does not indicate planned inventory306 matches self-discovered physical 302 and logical 304 inventories,network element inventory 106 may indicate that the inventories do notmatch or may choose one of the planned or self-discovered physical 302or logical inventory 304. Additionally, a repair ticket may be issued oran operation system may be notified to investigate the discrepancy. Insome cases, planned inventory 306 and self-discovered physical 302 andlogical 304 inventories do not overlap and thus, just the planned 306 orself-discovered physical 302 and logical 304 information is included inthe view.

As described above, network element inventory 106 is constantly accessedby different operation systems. For example, sales 402, marketing 404,and engineering 406 within an organization are different operationsystems and require different views of the network element inventory.With the network continually changing, the departments may not receivean accurate view of the network inventory if network element inventory106 is not updated. Thus, in order to ensure an accurate view of thenetwork inventory, the network element inventory 106 is updated whenchanges, additions, or updates are made to the network in real-time.Additionally, network element inventory 106 may be updated when requestsare made or on a periodic basis.

Thus, when changes, additions, and/or updates are made to the networkand are received by network element inventory 106, they are synchronizedwith existing inventory. Once network element inventory 106 issynchronized, new views may be sent to the operation systems.Alternatively, new views may be provided only when they are requestedand/or on a periodic basis. Thus, operation systems will be accessingaccurate and current data from network element inventory 106.

Planned network inventory 306 is synchronized when changes or additionsare made to network 102. For example, port/card updates areautomatically synchronized when changes are made to the port/cards orport/cards are added to network 102. Additionally, IOF/Fiber inventoryis automatically updated and synchronized. Further, changes to VCI/VPIpools are automatically updated and synchronized. Thus, when a requestfor a view of network element inventory 106 is made, the inventory maybe updated and synchronized before the view is sent to the requester.Therefore, an accurate and up-to-date view of the network inventory isprovided. Additionally, when changes in the network element inventoryare discovered, synchronized views may be sent to different operationsystems automatically.

Physical 302 and logical 304 inventory is updated by network 102 selfdiscovering the installed network elements. The update may be donenightly or in non-real-time, or may be done on a real-time basis using apolling process that automatically creates a current network inventory.Once the network is self-discovered, the self-discovered inventory issynchronized with the existing network element inventory. Thus, when arequest is made, network element inventory 106 may be synchronized withnon-real-time or real-time data before returning the request.

FIG. 5 illustrates a method for managing a network element inventoryaccording to one embodiment. In step S500, physical network inventory302 is self-discovered by network 102. Self-discovered physical networkinventory 302 may be discovered in real-time or non-real-time.

In step S502, logical network inventory 304 is self-discovered by thenetwork. Self-discovered logical network inventory 304 may be discoveredin real-time or non-real-time.

In step S504, planned network inventory 306 is provided. Once thephysical 302, logical 304, and planned 306 network inventory isdiscovered, the inventories are loaded into network element inventory106 (Step S506).

In step S508, physical 302, logical 304, and planned 306 inventories aresynchronized. In step S510, a request for a view of network elementinventory 106 is received. An accurate view of network element inventory106 is then provided (Step S512).

Uses of the Network Element Inventory Capacity Checking

FIG. 6 illustrates elements of a capacity calculating engine (CCE)environment 601 according to one embodiment. As shown, a capacitycalculating engine 600, sales graphical user interface (GUI) 604, otherapplications 606, and network element inventory 106 are shown.Additionally, network element inventory 106 includes held and pendingorder files.

Capacity calculating engine 600 receives requests for a determination ofcapacity for a network from sales consultants 608 and/or other users 610through sales GUI 604 or other applications 606. Once receiving arequest, CCE 600 communicates with network element inventory 106 toprovide a calculation on capacity of network 102. In one embodiment, thecapacity calculation is a calculation of possible and spare virtual andphysical capacity. Additionally, the calculation may include adetermination of network quality.

In one embodiment, capacity may be expressed in terms of possible andspare capacity. Possible capacity is a maximum number of users minus theenabled number of users for the network element. Maximum capacity is themaximum number of users a network element may support. However, thenetwork element may not be enabled to provide service for the maximumnumber of users. For example, the network element may only be enabled toprovide service for half of the maximum number. Thus, possible capacityis the capacity not enabled to provide service. Spare capacity takes theenabling number into account and determines capacity as the number ofusers the network element is enabled to provide service minus the numberof users currently using the service. For example, the network elementmay include a maximum number of ten ports. However, only five of theports may be enabled to provide service. Of those five ports, threeports may be in use presently. Thus, possible capacity is five ports andspare capacity is two ports. In other words, two ports may beimmediately enabled for service and five additional ports are availableto provide service if enabled.

In one embodiment, capacity checking engine 600 determines spare VDSLport capacity of CO DSLAM 230 and RT DSLAM 236, such as BDTs, ONUs,USAMs, BNUs, and MDUs. Although the following description will bedescribed in terms of capacity for these units, it will be understood bya person of skill in the art that capacity checking engine 600 may beable to check other network element capacities and is not limited tojust VDSL port capacities.

In one embodiment, possible and spare capacity is calculated based onvariations of video/data port capacities in different network elements.For example, the following table illustrates various RT DSLAM 236 typesand their maximum video/data port capacity and maximum telephone portcapacities according to one embodiment.

Maximum Video/Data Port Maximum Tel RT Type Capacity Port Capacity BNU-88 12 BNU-16 & MDU 16 24 BNU-1636 16 36 USAM Split Brain Mode (OC-3) 32USAM Single Mode (OC-3) 16 USAM Single Mode (OC-12) 32

RT DSLAM 236 Port Capacities

It should be understood that a reference table is being provided as anexample and many variations of this table are contemplated.

In one embodiment, capacity checking engine 600 may check network 102for network quality to ensure the network is properly configured tooffer service to the service area identifier. CCE 600 may set flags orreturn codes that indicate the quality of network 102. The followingtable illustrates examples of possible return codes according to oneembodiment.

Normal Empty slots available for service BNU Telephony capacityexhausted One or more invalid input cable name format Central office notfound One or more BDT/ODU combinations not found Too many BNU/MDUderived cables Fatal error TBD - future

Return Codes Conditions

It should be understood that the conditions in the table are notmutually exclusive and any combination of these conditions may bereturned. Also, the flags or return codes are not limited to the codesshown in the table.

FIG. 7 illustrates a method of determining capacity for network 102according to one embodiment. In one embodiment, capacity may beexpressed in port quantities. In another embodiment, capacity may beexpressed in terms of card or slot quantities. Cards or slots include anumber of ports, such as two. The ports in the cards or slots areenabled to serve customers. In step S700, a request for capacity isreceived by capacity calculating engine 600. The request includes aservice area identifier, which identifies a particular customer or groupof customers. In one embodiment, the service area identifier may be atelephone number. The service area identifier is used to identifynetwork elements or a path of network elements in network 102. In oneembodiment, the identifier may include a wire center CLLI code (code ofa CO 206) or cable designators for a RT DSLAM 236 (Fiber to the Nodeconfiguration) to cross box or RT DSLAM 236 (Fiber to the Curbconfiguration) to a service area identifier cable.

In one embodiment, the identifier is parsed to determine if it is in theproper format. An appropriate response code flag is then set. Forexample, a response code flag, such as one or more invalid input cablename format, is set if cable designators are not in a proper format. Ifall cable designations are not in a proper format, a fatal error may bereturned. In step S702, network element inventory 106 is queried fordata relating to the service area identifier. In one embodiment, a listof network elements related to the service area identifier is returned.

In Step S704, CCE 600 determines the network elements to be checked fromthe service area identifier. Additionally, CCE 600 may test for and seta response code flag for either of the following conditions if eitherexist: if the information received from network element inventory 106indicates CO 206 is not in the database, a flag, such as “central officenot found” or “fatal error,” may be returned, or if the receivedinformation indicates an RT is connected to central office 206 is not inthe database, a flag indicating “one or more CO 206/RT DSLAM 236combinations are not found” may be returned. Further, if all discoveredCO 206/RT DSLAM 236 combinations are not in the database, a fatal errorresponse may be returned. Also, fiber connections, such as OC-3 c andOC-12 c and special RT DSLAM 236 configurations, such as split brainmode, may be tested.

In one embodiment, CCE 600 may check and determine if telephony usage isat a maximum. In one embodiment, if RT DSLAM 236 and/or data serviceusage is at a maximum, a response code flag indicating that “plain oldtelephone service (POTS) usage is at a maximum” may be set.

In Step S706, the identified equipment is checked to determine if theidentified equipment has possible capacity available. In one embodiment,CCE 600 takes the maximum number of ports minus the number of portspresent to determine the possible capacity. In one embodiment, CCE 600may also determine a number of possible cards or slots available forservice. In one embodiment, a response flag, such as “empty slotsavailable for service” may be set if the number of ports present in theidentified equipment are less than the maximum supported number ofports.

In Step S708, the spare video/data port capacity is calculated for eachnetwork element identified. CCE 600 determines the number of video/dataports present and the number of video/data ports in use for each networkelement identified. In one embodiment, the spare video/data portcapacity is calculated as video/data ports present less the video/dataports in use. The calculation represents the number of spare physicalports that are presently available for service activation.

In another embodiment, the spare capacity calculation includes using anumber of defective port/card slots and the number of possible port/cardslots. In this embodiment, CCE 600 calculates spare capacity as thecalculated spare capacity plus the number of possible video/data portsor cards minus the number of defective ports or cards.

CCE 600 adds the number of possible video/data ports to the sparecapacity. By adding the number of possible video/data ports, servicewill not be denied if service may be offered by the network even ifadditional maintenance is needed to enable the possible video/dataports. Also, the number of possible video/data ports may be added as 2video/data ports per possible card slot. In this case, it is assumedthat there are 2 video/data ports per card or slot.

Additionally, CCE 600 subtracts the number of defective ports from thespare capacity. By subtracting the number of defective ports, a moreaccurate view of capacity is presented. A port may have been enabled forservice but for some reason is defective and cannot deliver service.Thus, the defective port is not considered available for service.Additionally, defective possible ports are not taken into account in thecapacity calculation. Also, the calculation may use cards instead ofports. In one embodiment, the number of defective video/data ports maybe subtracted as 2 video/data ports per defective card slot. In thiscase, it is assumed that there are 2 video/data ports per card or slot.

In another embodiment, CCE 600 may use a number of held and pendingorders to calculate spare capacity. In this embodiment, the CCE willcompute the spare video/data ports capacity as the calculated sparevideo/data ports less the number of held or pending orders for the videoservice. The held and pending orders for the data service are notconsidered by the capacity checking engine. A reason video service heldand pending orders are considered and not the data service held andpending orders is because the video service is given priority over dataservice. One reason video service is given priority is because of thepotential for greater profits. However, in other embodiments, the dataservice held and pending orders may take priority over the video serviceor both the video and data service held and pending orders may be takeninto consideration. The held and pending orders for video service aretaken into account because capacity for pending video service shouldpreferably not be taken up by other orders. A service provider does notwant to replace a held and pending video service order with a dataservice order.

In another embodiment, the spare video/data port capacity may be brokendown by distinguishing between video and data. For example, a number ofdata only ports in the spare video/data ports is returned with the sparecapacity calculation. Different combinations of services may be enabledfor a port. For example, a port may be enabled for video and data,video-only, and data-only. In one embodiment, it is desired to enableports with video services and thus, priority is given to video and dataservice, and video only services. A reason for giving video priority isit is expected that video services are more profitable than dataservices. Thus, if the number of spare data-only ports are known, theremaining spare ports may be reserved for video, and data or video-onlyservices. Thus, spare video data ports reserved for video services willnot be reserved by data-only services. However, in other embodiments,data services may be given priority over video services. The goal is togive priority to the most profitable services.

In Step S710, a response is assembled and sent to the requester. In oneembodiment, the total spare video/data port capacity for the servicearea identifier is reported. The total is the sum of the spare ports ofeach individual network element identified. The response may include anyof the above calculations of spare capacity. Also, the response mayinclude all the set response code flags indicating network quality.

Additionally, in one embodiment, the response message may include thefollowing: the received wire center CLLI code, received cabledesignation(s), the parsed CO 206/RT DSLAM 236 combination, the setresponse code flags, and/or a spares available yes/no indicator. In oneembodiment, the yes flag will be sent if the sum of the spare video/dataports at RT DSLAM 236 location is greater than five or if the sum of thespare video/data port at RT DSLAM 236 (Fiber to the Curb configuration)location is greater than one. If either of these conditions are not met,a no will be sent. In another embodiment, the spares available yes/noindicator will indicate yes if the total quality of the spare video/dataports is greater than zero for any of the available network elements forthe service area identifier. If there are not spare video/data ports,then a no will be indicated.

Additionally, for each network element checked, a CO DSLAM 230 and/or RTDSLAM 236 number, IP address, CK ID number, DSLAM type, RT DSLAM 236CLLI, address (location) and quantity of spare video/data ports presentmay be reported.

In one embodiment, if a failed error condition occurs with any of theabove determinations by the CCE 600, a response to the query may includethe following: a received wire center CLLI code received cabledestinations, available pairs, response code (indicating all setconditions including the fatal error flag), spares available yes/noindicator of no, and zero as a spare video/data port quantity.Additionally, no individual CO DSLAM 230 and/or RT DSLAM 236 assignmentinformation may be returned.

FIG. 8 illustrates a method for handling customer inquiries for videoand data service. Step S800, a customer inquires about possible serviceeither through the web or through a sales consultant. The salesconsultant then contacts the capacity checking engine to determine inreal-time the loop quality and service availability (Step S802). In stepS804, capacity checking engine 600 determines the loop quality of thenetwork and spare capacity for a service area identifier for thecustomer. If there is service availability and capacity, the salesconsultant may process the order for service (Step S808). However, ifcapacity is not available and/or there are not service availability, asales consultant will inform the customer that service is not available(Step S810). The sales consultant may approve or disapprove the requestfor service based on video and data port availability. The salesconsultant may not want to fill up all video/data ports for the servicearea identifier and may decide to put a data only request on hold (StepS812). However, a sales consultant wants to receive as many videorequests as possible and would approve a request for a video serviceover a data service (Step S814).

By using the CCE, a sales consultant is relieved of many manual tasks,such as referring to documents relating to capacity and also accessingcomputer databases and looking for and matching service area identifiersto entries in the database. These entries, in both cases, may be out ofdate. However, using the CCE, the requested data may be returned to theclient or sales consultant in less than 2 seconds or in most caseswithin 5 seconds. Thus, the CCE increases customer service and providesmore reliable service to customers requesting VDSL service.

In other embodiments, network element inventory 106 may be used toprovide an inventory history. Additionally, in another embodiment,network element inventory 106 may be used by a web portal that allowsusers to view and/or manage network element inventory 106.

The above description is illustrated but not restrictive. Manyvariations of the invention will become apparent to those skilled in theart upon review of this disclosure. The scope of the invention should,therefore, be determined not with reference to the above description,but instead should be determined with reference to the pending claimsalong with their full scope or equivalents.

1. A method for managing a network element inventory for a video anddata network comprising: self-discovering a physical network inventoryof physical network elements using network elements of the video anddata network; self-discovering a logical network inventory of logicalnetwork elements using network elements of the video and data network;providing a planned network inventory of the video and data network;loading the physical network inventory, logical network inventory, andplanned network inventory into the network element inventory, whereinthe physical network elements and logical network elements of the videoand data network change over time, wherein the physical networkinventory and logical network inventory is continually self-discoveredover the time period to update the physical network inventory andlogical network inventory in real-time; synchronizing the physicalnetwork inventory, logical network inventory, and planned networkinventory in the network element inventory to determine any differencesbetween the real-time updated physical network inventory and thereal-time updated logical network inventory with the planned networkinventory; receiving a request for a view of the network elementinventory; and determining the view based on at least one of thesynchronized physical network inventory, the synchronized logicalnetwork inventory, and planned network inventory, wherein the view isdetermined based on if any differences between physical network elementsof the real-time updated physical network inventory and logical networkelements of the real-time updated logical network inventory withphysical or logical network elements of the planned network inventoryare determined.
 2. The method of claim 1, wherein the video and datanetwork comprises a Very high bit rate Digital Subscriber Line (VDSL)network.
 3. The method of claim 1, wherein the video and data networkcomprises a Digital Subscriber Line (xDSL) network.
 4. The method ofclaim 1, wherein the planned network inventory comprises planned virtualnetwork inventory.
 5. The method of claim 1, wherein the planned networkinventory comprises planned physical network inventory.
 6. The method ofclaim 1, wherein synchronizing the physical network inventory, logicalnetwork inventory, and planned network inventory comprises comparing theplanned network inventory with the self-discovered real-time updatedphysical and real-time updated logical network inventory.
 7. The methodof claim 6, further comprising creating a repair ticket if thecomparison of the planned network inventory with the self-discoveredreal-time updated physical and real-time updated logical networkinventory is not substantially equal.
 8. The method of claim 1, whereinif differences between the self-discovered real-time updated physicalnetwork inventory and the self-discovered real-time updated logicalnetwork inventory with the planned network inventory are determined,determining the view comprising: providing the view with the differencesand at least one of the self-discovered real-time updated physicalnetwork inventory, self-discovered real-time updated logical networkinventory, and the planned network inventory.
 9. The method of claim 1,wherein if differences between the self-discovered real-time updatedphysical network inventory and the self-discovered real-time updatedlogical network inventory with the planned network inventory aredetermined, determining the view comprising: selecting one of theself-discovered real-time updated physical network inventory,self-discovered real-time updated logical network inventory, and theplanned network inventory for the view.
 10. A method for managing anetwork element inventory between one or more operation systems for avideo and data network comprising: self-discovering a physical networkinventory of physical network elements using network elements of thevideo and data network; self-discovering a logical network inventory oflogical network elements using network elements of the video and datanetwork; providing a planned network inventory of the video and datanetwork; loading the physical network inventory, logical networkinventory, and planned network inventory into the network elementinventory, wherein the physical network elements and logical networkelements of the video and data network change over time, wherein thephysical network inventory and logical network inventory is continuallyself-discovered over the time period to update the physical networkinventory and logical network inventory in real-time; synchronizing thephysical network inventory, logical network inventory, and plannednetwork inventory in the network element inventory to determine anydifferences between the real-time updated physical network inventory andthe real-time updated logical network inventory with the planned networkinventory; creating one or more views of the network element inventoryusing at least one of the synchronized physical network inventory, thesynchronized logical network inventory, and the planned networkinventory for the one or more operation systems, wherein the one or moreviews are created based on if any differences between physical networkelements of the real-time updated physical network inventory and logicalnetwork elements of the real-time updated logical network inventory withphysical or logical network elements of the planned network inventoryare determined; providing the one or more views to the one or moreoperation systems.
 11. The method of claim 10, further comprisingreceiving an update of self-discovered physical, self discoveredlogical, and planned inventory.
 12. The method of claim 11, furthercomprising re-synchronizing the physical network inventory, logicalnetwork inventory, and planned network inventory in the network elementinventory with the update of self-discovered physical, self discoveredlogical, and planned inventory.
 13. The method of claim 12, furthercomprising creating one or more views of the re-synchronized networkelement inventory for the one or more operation systems.
 14. The methodof claim 13, further comprising providing the one or more views usingthe re-synchronized physical network inventory, logical networkinventory, and planned network inventory.
 15. The method of claim 10,wherein the operation systems comprise sales, engineering, and marketingsystems.
 16. The method of claim 10, wherein the video and data networkcomprises a Very High bit rate Digital Subscriber Line (VDSL) network.17. The method of claim 10, wherein the video and data network comprisesan xDSL network.
 18. The method of claim 10, wherein the planned networkinventory comprises planned virtual network inventory.
 19. The method ofclaim 10, wherein the planned network inventory comprises plannedphysical network inventory.
 20. The method of claim 10, whereinsynchronizing the physical network inventory, logical network inventory,and planned network inventory comprises comparing the planned networkinventory with the self-discovered real-time updated physical andreal-time updated logical network inventory.
 21. The method of claim 20,further comprising creating a repair ticket if the comparison of theplanned network inventory with the self-discovered real-time updatedphysical and real-time updated logical network inventory is notsubstantially equal.
 22. The method of claim 10, wherein if differencesbetween the self-discovered real-time updated physical network inventoryand the self-discovered real-time updated logical network inventory withthe planned network inventory are determined, determining the viewcomprising: providing the view with the differences and at least one ofthe self-discovered real-time updated physical network inventory,self-discovered real-time updated logical network inventory, and theplanned network inventory.
 23. The method of claim 10, wherein ifdifferences between the self-discovered real-time updated physicalnetwork inventory and the self-discovered real-time updated logicalnetwork inventory with the planned network inventory are determined,determining the view comprising: selecting one of the self-discoveredreal-time updated physical network inventory, self-discovered 1real-time updated logical network inventory, and the planned networkinventory for the view.
 24. A method for managing a network elementinventory for a video and data network comprising: self-discovering aphysical network inventory of physical network elements using networkelements of the video and data network; self-discovering a logicalnetwork inventory of logical network elements using network elements ofthe video and data network; receiving a planned network inventory of thevideo and data network; storing the physical network inventory, logicalnetwork inventory, and planned network inventory into the networkelement inventory, wherein the physical network elements and logicalnetwork elements of the video and data network change over time, whereinthe physical network inventory and logical network inventory iscontinually self-discovered over the time period to update the physicalnetwork inventory and logical network inventory in real-time; andcomparing the physical network inventory, logical network inventory, andplanned network inventory in the network element inventory to determinedifferences between the real-time updated physical network inventory andthe real-time updated logical network inventory with the planned networkinventory; and determining a view of the network element inventory basedon at least one of the physical network inventory, logical networkinventory, planned network inventory, and the comparison betweenphysical network elements of the real-time updated physical networkinventory and logical network elements of the real-time updated logicalnetwork inventory with physical or logical network elements of theplanned network inventory.
 25. The method of claim 24, wherein theplanned network inventory comprises planned virtual network inventory.26. The method of claim 24, wherein the planned network inventorycomprises planned physical network inventory.
 27. The method of claim24, further comprising: receiving a request for a view of the networkelement inventory; and providing the view using at least one of thephysical network inventory, logical network inventory, planned networkinventory, and the comparison between the real-time updated physicalnetwork inventory and the real-time updated logical network inventorywith the planned network inventory.
 28. The method of claim 24, furthercomprising if there are differences between the real-time updatedphysical network inventory and the real-time updated logical networkinventory with the planned network inventory, selecting at least one ofthe real-time updated physical network inventory, the real-time updatedlogical network inventory, and the planned network inventory as arepresentation of the network element inventory.
 29. The method of claim24, further comprising if there are differences between the real-timeupdated physical network inventory and the real-time updated logicalnetwork inventory with the planned network inventory, determining arepresentation of the network element inventory from the real-timeupdated physical network inventory, the real-time updated logicalnetwork inventory, and the planned network inventory.
 30. The method ofclaim 24, further comprising receiving an update of at least one of theself-discovered physical, self discovered logical, and plannedinventory.
 31. The method of claim 30, further comprising comparing anupdated physical network inventory or updated logical network inventorywith an updated planned network inventory in the network elementinventory to determine differences between the updated physical networkinventory and the logical network inventory with the planned networkinventory.
 32. An apparatus for managing a network element inventory fora video and data network, the apparatus comprising: a self-discoveredphysical network inventory of physical network elements using networkelements of the video and data network; a self-discovered logicalnetwork inventory of logical network elements using network elements ofthe video and data network; a planned network inventory of the video anddata network; a database for storing the physical network inventory,logical network inventory, and planned network inventory into thenetwork element inventory, wherein the physical network elements andlogical network elements of the video and data network change over time,wherein the physical network inventory and logical network inventory iscontinually self-discovered over the time period to update the physicalnetwork inventory and logical network inventory in real-time; logicconfigured to compare the physical network inventory, logical networkinventory, and planned network inventory in the network elementinventory to determine differences between the real-time updatedphysical network inventory and the real-time updated logical networkinventory with the planned network inventory; and logic to determine aview of the network element inventory based on at least one of thephysical network inventory, logical network inventory, planned networkinventory, and the comparison between physical network elements of thereal-time updated physical network inventory and logical networkelements of the real-time updated logical network inventory withphysical or logical network elements of the planned network inventory.33. The apparatus of claim 32, further comprising: logic to receive arequest for a view of the network element inventory; and logic toprovide the view using at least one of the real-time updated physicalnetwork inventory, real-time updated logical network inventory, andplanned network inventory.
 34. The apparatus of claim 32, wherein theplanned network inventory comprises planned virtual network inventory.35. The apparatus of claim 32, wherein the planned network inventorycomprises planned physical network inventory.